I have test it and it works. Need a review and merge.

maybe we can even improove it by adding a magic wand matching
and provide an advance guess where we check with

• lower case equal
• field name contain column name

but we need a validation layout with:
original name and column name proposition with a validation.

wdyt ?
anyway it need a new issue for that.

Hi @dufoli,
Thanks for the PR !

Could you create your branch from releaseCandidate and use this target branch when updating the PR ?
Also could you reference your change in CHANGES.md file following current convention ?
Thanks

@tprouvot that s done ;-)

Hi @dufoli ,

I'm facing an issue during my tests, could you have a check ?
Thanks !

J'ai corrigé.

I have improved it by adding a refresh function in order to guess all column after change of object type (by selection or auto selection when it is guessed from first column of import.

ready for new review

rebase

@tprouvot any news for review ?

@dufoli
Is the PR ready to test ?

Yes

I have take another look and see that i remove trim by mistake

Hey @dufoli happy new year !
Sorry but the auto detect does not work anymore, could you have a check ?

hello, I have recheck. It is a matter of async call of describeInfo because didUpdate do nothing and when we call for first time cache of object is empty. So I have change the way of update by doing it in async way if didupdate is call and in direct way if already present.